stable | AppUnix

Stable kernel 2.6.34.10

28/06/2011 by OwnServer

Lançado kernel 2.6.34.10 estável. Para conferir parte das notas de lançamento:

commit 0eafe6686c56b91d436265c9098e72a1f8ab4f19
Author: Paul Gortmaker &lt;paul.gortmaker@windriver.com&gt;
Date:   Sun Jun 26 12:47:42 2011 -0400

    Linux 2.6.34.10

commit 83264a0f19be3fe69f5c9048210bb39402fb57db
Author: Al Viro &lt;viro@ftp.linux.org.uk&gt;
Date:   Tue Sep 28 18:50:27 2010 +0100

    MIPS: secure_computing, syscall audit: syscall number should in r2, not r0.

    commit e5b377a8fb7b05f27647698ac739a0504cb2bf80 upstream.

    As it is, audit_syscall_entry() and secure_computing() get the
    bogus value (0, in fact)

    Signed-off-by: Al Viro &lt;viro@zeniv.linux.org.uk&gt;
    Cc: linux-kernel@vger.kernel.org
    Cc: linux-arch@vger.kernel.org
    Cc: linux-mips@linux-mips.org
    Patchwork: https://patchwork.linux-mips.org/patch/1697/
    Signed-off-by: Ralf Baechle &lt;ralf@linux-mips.org&gt;
    Signed-off-by: Paul Gortmaker &lt;paul.gortmaker@windriver.com&gt;

commit 48adbc4b330cefb3b77111e47c17e833404893ef
Author: Linus Torvalds &lt;torvalds@linux-foundation.org&gt;
Date:   Thu Oct 28 15:40:55 2010 +0000

    net: fix rds_iovec page count overflow

    commit 1b1f693d7ad6d193862dcb1118540a030c5e761f upstream.

    As reported by Thomas Pollet, the rdma page counting can overflow.  We
    get the rdma sizes in 64-bit unsigned entities, but then limit it to
    UINT_MAX bytes and shift them down to pages (so with a possible "+1" for
    an unaligned address).

    So each individual page count fits comfortably in an 'unsigned int' (not
    even close to overflowing into signed), but as they are added up, they
    might end up resulting in a signed return value. Which would be wrong.

    Catch the case of tot_pages turning negative, and return the appropriate
    error code.

    [PG: In 34, var names are slightly different, 1b1f6's tot_pages is
     34's nr_pages, and 1b1f6's nr_pages is 34's nr; so map accordingly.]

    Reported-by: Thomas Pollet &lt;thomas.pollet@gmail.com&gt;
    Signed-off-by: Linus Torvalds &lt;torvalds@linux-foundation.org&gt;
    Signed-off-by: Andy Grover &lt;andy.grover@oracle.com&gt;
    Signed-off-by: David S. Miller &lt;davem@davemloft.net&gt;
    Signed-off-by: Paul Gortmaker &lt;paul.gortmaker@windriver.com&gt;

commit e0843d17d6d9997f23534f1ffe9dafb0d5912636
Author: Vasiliy Kulikov &lt;segoon@openwall.com&gt;
Date:   Thu Mar 17 01:40:10 2011 +0000

    econet: 4 byte infoleak to the network

    commit 67c5c6cb8129c595f21e88254a3fc6b3b841ae8e upstream.

    struct aunhdr has 4 padding bytes between 'pad' and 'handle' fields on
    x86_64.  These bytes are not initialized in the variable 'ah' before
    sending 'ah' to the network.  This leads to 4 bytes kernel stack
    infoleak.

    This bug was introduced before the git epoch.

    Signed-off-by: Vasiliy Kulikov &lt;segoon@openwall.com&gt;
    Acked-by: Phil Blundell &lt;philb@gnu.org&gt;
    Signed-off-by: David S. Miller &lt;davem@davemloft.net&gt;
    Signed-off-by: Paul Gortmaker &lt;paul.gortmaker@windriver.com&gt;

commit 3e3b57978a0e1140d91f09d3a4197b6411b18f12
Author: Vasiliy Kulikov &lt;segoon@openwall.com&gt;
Date:   Tue Mar 15 13:37:13 2011 +0100

    ipv6: netfilter: ip6_tables: fix infoleak to userspace

    commit 6a8ab060779779de8aea92ce3337ca348f973f54 upstream.

    Structures ip6t_replace, compat_ip6t_replace, and xt_get_revision are
    copied from userspace.  Fields of these structs that are
    zero-terminated strings are not checked.  When they are used as argument
    to a format string containing "%s" in request_module(), some sensitive
    information is leaked to userspace via argument of spawned modprobe
    process.

    The first bug was introduced before the git epoch;  the second was
    introduced in 3bc3fe5e (v2.6.25-rc1);  the third is introduced by
    6b7d31fc (v2.6.15-rc1).  To trigger the bug one should have
    CAP_NET_ADMIN.

    Signed-off-by: Vasiliy Kulikov &lt;segoon@openwall.com&gt;
    Signed-off-by: Patrick McHardy &lt;kaber@trash.net&gt;
    Signed-off-by: Paul Gortmaker &lt;paul.gortmaker@windriver.com&gt;

commit 1d9064bb2d8f0ea26a67b2ce74c6d1d461dcfe7d
Author: Vasiliy Kulikov &lt;segoon@openwall.com&gt;
Date:   Tue Mar 15 13:36:05 2011 +0100

    netfilter: ip_tables: fix infoleak to userspace

    commit 78b79876761b86653df89c48a7010b5cbd41a84a upstream.

    Structures ipt_replace, compat_ipt_replace, and xt_get_revision are
    copied from userspace.  Fields of these structs that are
    zero-terminated strings are not checked.  When they are used as argument
    to a format string containing "%s" in request_module(), some sensitive
    information is leaked to userspace via argument of spawned modprobe
    process.

    The first and the third bugs were introduced before the git epoch; the
    second was introduced in 2722971c (v2.6.17-rc1).  To trigger the bug
    one should have CAP_NET_ADMIN.

    Signed-off-by: Vasiliy Kulikov &lt;segoon@openwall.com&gt;
    Signed-off-by: Patrick McHardy &lt;kaber@trash.net&gt;
    Signed-off-by: Paul Gortmaker &lt;paul.gortmaker@windriver.com&gt;

commit f1f486501fa9b401c762b2355a238cf9e7f18385
Author: Vasiliy Kulikov &lt;segoon@openwall.com&gt;
Date:   Tue Mar 15 13:35:21 2011 +0100

    netfilter: arp_tables: fix infoleak to userspace

    commit 42eab94fff18cb1091d3501cd284d6bd6cc9c143 upstream.

    Structures ipt_replace, compat_ipt_replace, and xt_get_revision are
    copied from userspace.  Fields of these structs that are
    zero-terminated strings are not checked.  When they are used as argument
    to a format string containing "%s" in request_module(), some sensitive
    information is leaked to userspace via argument of spawned modprobe
    process.

    The first bug was introduced before the git epoch;  the second is
    introduced by 6b7d31fc (v2.6.15-rc1);  the third is introduced by
    6b7d31fc (v2.6.15-rc1).  To trigger the bug one should have
    CAP_NET_ADMIN.

    Signed-off-by: Vasiliy Kulikov &lt;segoon@openwall.com&gt;
    Signed-off-by: Patrick McHardy &lt;kaber@trash.net&gt;
    Signed-off-by: Paul Gortmaker &lt;paul.gortmaker@windriver.com&gt;

commit 41c6364db6028e2776250be12961b30f4a2ffbf9
Author: Vasiliy Kulikov &lt;segoon@openwall.com&gt;
Date:   Mon Feb 14 16:49:23 2011 +0100

    bridge: netfilter: fix information leak

    commit d846f71195d57b0bbb143382647c2c6638b04c5a upstream.

    Struct tmp is copied from userspace.  It is not checked whether the "name"
    field is NULL terminated.  This may lead to buffer overflow and passing
    contents of kernel stack as a module name to try_then_request_module() and,
    consequently, to modprobe commandline.  It would be seen by all userspace
    processes.

    Signed-off-by: Vasiliy Kulikov &lt;segoon@openwall.com&gt;
    Signed-off-by: Patrick McHardy &lt;kaber@trash.net&gt;
    Signed-off-by: Paul Gortmaker &lt;paul.gortmaker@windriver.com&gt;

commit 26b6a59e8b70435996c86f705dfb7f66124f5b1e
Author: Vasiliy Kulikov &lt;segoon@openwall.com&gt;
Date:   Mon Feb 14 13:54:31 2011 +0300

    Bluetooth: bnep: fix buffer overflow

    commit 43629f8f5ea32a998d06d1bb41eefa0e821ff573 upstream.

    Struct ca is copied from userspace.  It is not checked whether the "device"
    field is NULL terminated.  This potentially leads to BUG() inside of
    alloc_netdev_mqs() and/or information leak by creating a device with a name
    made of contents of kernel stack.

    Signed-off-by: Vasiliy Kulikov &lt;segoon@openwall.com&gt;
    Signed-off-by: Gustavo F. Padovan &lt;padovan@profusion.mobi&gt;
    Signed-off-by: Paul Gortmaker &lt;paul.gortmaker@windriver.com&gt;

commit f8107dd119c9fd62aa0a3d3eb55d67bdd84b8036
Author: Vasiliy Kulikov &lt;segoon@openwall.com&gt;
Date:   Mon Feb 14 13:54:26 2011 +0300

    Bluetooth: sco: fix information leak to userspace

    commit c4c896e1471aec3b004a693c689f60be3b17ac86 upstream.

    struct sco_conninfo has one padding byte in the end.  Local variable
    cinfo of type sco_conninfo is copied to userspace with this uninizialized
    one byte, leading to old stack contents leak.

    Signed-off-by: Vasiliy Kulikov &lt;segoon@openwall.com&gt;
    Signed-off-by: Gustavo F. Padovan &lt;padovan@profusion.mobi&gt;
    Signed-off-by: Paul Gortmaker &lt;paul.gortmaker@windriver.com&gt;

commit 973800f01aa1ab2bf5b8a412af07fc2cc568c783
Author: Alex Elder &lt;aelder@sgi.com&gt;
Date:   Tue Mar 1 17:50:00 2011 +0000

    xfs: zero proper structure size for geometry calls

    commit af24ee9ea8d532e16883251a6684dfa1be8eec29 upstream.

    Commit 493f3358cb289ccf716c5a14fa5bb52ab75943e5 added this call to
    xfs_fs_geometry() in order to avoid passing kernel stack data back
    to user space:

    +       memset(geo, 0, sizeof(*geo));

    Unfortunately, one of the callers of that function passes the
    address of a smaller data type, cast to fit the type that
    xfs_fs_geometry() requires.  As a result, this can happen:

    Kernel panic - not syncing: stack-protector: Kernel stack is corrupted
    in: f87aca93

    Pid: 262, comm: xfs_fsr Not tainted 2.6.38-rc6-493f3358cb2+ #1
    Call Trace:

    [&lt;c12991ac&gt;] ? panic+0x50/0x150
    [&lt;c102ed71&gt;] ? __stack_chk_fail+0x10/0x18
    [&lt;f87aca93&gt;] ? xfs_ioc_fsgeometry_v1+0x56/0x5d [xfs]

    Fix this by fixing that one caller to pass the right type and then
    copy out the subset it is interested in.

    Note: This patch is an alternative to one originally proposed by
    Eric Sandeen.

    Reported-by: Jeffrey Hundstad &lt;jeffrey.hundstad@mnsu.edu&gt;
    Signed-off-by: Alex Elder &lt;aelder@sgi.com&gt;
    Reviewed-by: Eric Sandeen &lt;sandeen@redhat.com&gt;
    Tested-by: Jeffrey Hundstad &lt;jeffrey.hundstad@mnsu.edu&gt;
    Signed-off-by: Paul Gortmaker &lt;paul.gortmaker@windriver.com&gt;

commit 5658d0e0d4830af95fcde40bc7c6db2dec8ebddf
Author: Dan Rosenberg &lt;drosenberg@vsecurity.com&gt;
Date:   Mon Feb 14 13:45:28 2011 +0000

    xfs: prevent leaking uninitialized stack memory in FSGEOMETRY_V1

    commit 3a3675b7f23f83ca8c67c9c2b6edf707fd28d1ba upstream.

    The FSGEOMETRY_V1 ioctl (and its compat equivalent) calls out to
    xfs_fs_geometry() with a version number of 3.  This code path does not
    fill in the logsunit member of the passed xfs_fsop_geom_t, leading to
    the leaking of four bytes of uninitialized stack data to potentially
    unprivileged callers.

    v2 switches to memset() to avoid future issues if structure members
    change, on suggestion of Dave Chinner.

    Signed-off-by: Dan Rosenberg &lt;drosenberg@vsecurity.com&gt;
    Reviewed-by: Eugene Teo &lt;eugeneteo@kernel.org&gt;
    Signed-off-by: Alex Elder &lt;aelder@sgi.com&gt;
    Signed-off-by: Paul Gortmaker &lt;paul.gortmaker@windriver.com&gt;

commit 11c66be05f49f70a635a6eb63e6cffea520b22c5
Author: Dan Rosenberg &lt;drosenberg@vsecurity.com&gt;
Date:   Sun Dec 26 06:54:53 2010 +0000

    CAN: Use inode instead of kernel address for /proc file

    commit 9f260e0efa4766e56d0ac14f1aeea6ee5eb8fe83 upstream.

    Since the socket address is just being used as a unique identifier, its
    inode number is an alternative that does not leak potentially sensitive
    information.

    CC-ing stable because MITRE has assigned CVE-2010-4565 to the issue.

    Signed-off-by: Dan Rosenberg &lt;drosenberg@vsecurity.com&gt;
    Acked-by: Oliver Hartkopp &lt;socketcan@hartkopp.net&gt;
    Signed-off-by: David S. Miller &lt;davem@davemloft.net&gt;
    Signed-off-by: Paul Gortmaker &lt;paul.gortmaker@windriver.com&gt;

commit 5cf8a08026f539f396a3170d1991d651ee0fb30c
Author: Dan Rosenberg &lt;drosenberg@vsecurity.com&gt;
Date:   Wed Dec 22 13:58:27 2010 +0000

    irda: prevent integer underflow in IRLMP_ENUMDEVICES

    commit fdac1e0697356ac212259f2147aa60c72e334861 upstream.

    If the user-provided len is less than the expected offset, the
    IRLMP_ENUMDEVICES getsockopt will do a copy_to_user() with a very large
    size value.  While this isn't be a security issue on x86 because it will
    get caught by the access_ok() check, it may leak large amounts of kernel
    heap on other architectures.  In any event, this patch fixes it.

    Signed-off-by: Dan Rosenberg &lt;drosenberg@vsecurity.com&gt;
    Signed-off-by: David S. Miller &lt;davem@davemloft.net&gt;
    Signed-off-by: Paul Gortmaker &lt;paul.gortmaker@windriver.com&gt;

commit 32e92da012e081ce4f741974761e92b215ff58b5
Author: Nelson Elhage &lt;nelhage@ksplice.com&gt;
Date:   Wed Nov 3 16:35:40 2010 +0000

    netlink: Make nlmsg_find_attr take a const nlmsghdr*.

    commit 6b8c92ba07287578718335ce409de8e8d7217e40 upstream.

    This will let us use it on a nlmsghdr stored inside a netlink_callback.

    Signed-off-by: Nelson Elhage &lt;nelhage@ksplice.com&gt;
    Signed-off-by: David S. Miller &lt;davem@davemloft.net&gt;
    Signed-off-by: Paul Gortmaker &lt;paul.gortmaker@windriver.com&gt;

commit 02e6f1ee075a325dc9079b3dc143d898e924ce64
Author: Nelson Elhage &lt;nelhage@ksplice.com&gt;
Date:   Wed Nov 3 16:35:41 2010 +0000

    inet_diag: Make sure we actually run the same bytecode we audited.

    commit 22e76c849d505d87c5ecf3d3e6742a65f0ff4860 upstream.

    We were using nlmsg_find_attr() to look up the bytecode by attribute when
    auditing, but then just using the first attribute when actually running
    bytecode. So, if we received a message with two attribute elements, where only
    the second had type INET_DIAG_REQ_BYTECODE, we would validate and run different
    bytecode strings.

    Fix this by consistently using nlmsg_find_attr everywhere.

    Signed-off-by: Nelson Elhage &lt;nelhage@ksplice.com&gt;
    Signed-off-by: Thomas Graf &lt;tgraf@infradead.org&gt;
    Signed-off-by: David S. Miller &lt;davem@davemloft.net&gt;
    Signed-off-by: Paul Gortmaker &lt;paul.gortmaker@windriver.com&gt;

commit ddfd87424bef1dc8b2930acae2311b286ab9de12
Author: Kulikov Vasiliy &lt;segooon@gmail.com&gt;
Date:   Sun Oct 31 07:10:32 2010 +0000

    net: tipc: fix information leak to userland

    commit 88f8a5e3e7defccd3925cabb1ee4d3994e5cdb52 upstream.

    Structure sockaddr_tipc is copied to userland with padding bytes after
    "id" field in union field "name" unitialized.  It leads to leaking of
    contents of kernel stack memory.  We have to initialize them to zero.

    Signed-off-by: Vasiliy Kulikov &lt;segooon@gmail.com&gt;
    Signed-off-by: David S. Miller &lt;davem@davemloft.net&gt;
    Signed-off-by: Paul Gortmaker &lt;paul.gortmaker@windriver.com&gt;

commit 262b3d2e9f111516bf5cc1211f9128180e0329ef
Author: Vasiliy Kulikov &lt;segooon@gmail.com&gt;
Date:   Wed Nov 10 10:14:33 2010 -0800

    net: ax25: fix information leak to userland

    commit fe10ae53384e48c51996941b7720ee16995cbcb7 upstream.

    Sometimes ax25_getname() doesn't initialize all members of fsa_digipeater
    field of fsa struct, also the struct has padding bytes between
    sax25_call and sax25_ndigis fields.  This structure is then copied to
    userland.  It leads to leaking of contents of kernel stack memory.

    Signed-off-by: Vasiliy Kulikov &lt;segooon@gmail.com&gt;
    Signed-off-by: David S. Miller &lt;davem@davemloft.net&gt;
    Signed-off-by: Paul Gortmaker &lt;paul.gortmaker@windriver.com&gt;

commit 44a214c1611386aa49ce86c70ebcddcad8a7a3f0
Author: Stuart Hayes &lt;stuart_hayes@yahoo.com&gt;
Date:   Wed Mar 2 13:42:05 2011 +0100

    dcdbas: force SMI to happen when expected

    commit dd65c736d1b5312c80c88a64bf521db4959eded5 upstream.

    The dcdbas driver can do an I/O write to cause a SMI to occur.  The SMI handler
    looks at certain registers and memory locations, so the SMI needs to happen
    immediately.  On some systems I/O writes are posted, though, causing the SMI to
    happen well after the "outb" occurred, which causes random failures.  Following
    the "outb" with an "inb" forces the write to go through even if it is posted.

    Signed-off-by: Stuart Hayes &lt;stuart_hayes@yahoo.com&gt;
    Acked-by: Doug Warzecha &lt;douglas_warzecha@dell.com&gt;
    Signed-off-by: Jiri Kosina &lt;jkosina@suse.cz&gt;
    Signed-off-by: Paul Gortmaker &lt;paul.gortmaker@windriver.com&gt;

commit e4b2f0cae9c5cd1d5a0959ee529e6a6fee620c5c
Author: Josef Bacik &lt;josef@redhat.com&gt;
Date:   Thu Nov 18 20:52:55 2010 -0500

    fs: call security_d_instantiate in d_obtain_alias V2

    commit 24ff6663ccfdaf088dfa7acae489cb11ed4f43c4 upstream

    While trying to track down some NFS problems with BTRFS, I kept noticing I was
    getting -EACCESS for no apparent reason.  Eric Paris and printk() helped me
    figure out that it was SELinux that was giving me grief, with the following
    denial

    type=AVC msg=audit(1290013638.413:95): avc:  denied  { 0x800000 } for  pid=1772
    comm="nfsd" name="" dev=sda1 ino=256 scontext=system_u:system_r:kernel_t:s0
    tcontext=system_u:object_r:unlabeled_t:s0 tclass=file

    Turns out this is because in d_obtain_alias if we can't find an alias we create
    one and do all the normal instantiation stuff, but we don't do the
    security_d_instantiate.

    Usually we are protected from getting a hashed dentry that hasn't yet run
    security_d_instantiate() by the parent's i_mutex, but obviously this isn't an
    option there, so in order to deal with the case that a second thread comes in
    and finds our new dentry before we get to run security_d_instantiate(), we go
    ahead and call it if we find a dentry already.  Eric assures me that this is ok
    as the code checks to see if the dentry has been initialized already so calling
    security_d_instantiate() against the same dentry multiple times is ok.  With
    this patch I'm no longer getting errant -EACCESS values.

    Signed-off-by: Josef Bacik &lt;josef@redhat.com&gt;
    Signed-off-by: Al Viro &lt;viro@zeniv.linux.org.uk&gt;
    Signed-off-by: Paul Gortmaker &lt;paul.gortmaker@windriver.com&gt;

commit 0ec63bc8c16763ab565ab97d39f10eb9a6ab9125
Author: Robin Holt &lt;holt@sgi.com&gt;
Date:   Wed Jan 12 17:00:01 2011 -0800

    epoll: convert max_user_watches to long

    commit 52bd19f7691b2ea6433aef0ef94c08c57efd7e79 upstream.

    On a 16TB machine, max_user_watches has an integer overflow.  Convert it
    to use a long and handle the associated fallout.

    Signed-off-by: Robin Holt &lt;holt@sgi.com&gt;
    Cc: "Eric W. Biederman" &lt;ebiederm@xmission.com&gt;
    Acked-by: Davide Libenzi &lt;davidel@xmailserver.org&gt;
    Cc: Pekka Enberg &lt;penberg@cs.helsinki.fi&gt;
    Signed-off-by: Andrew Morton &lt;akpm@linux-foundation.org&gt;
    Signed-off-by: Linus Torvalds &lt;torvalds@linux-foundation.org&gt;
    Signed-off-by: Paul Gortmaker &lt;paul.gortmaker@windriver.com&gt;

O resto pode ser visto em: <a href="http://www.kernel.org/pub/linux/kernel/v2.6/longterm/v2.6.34/ChangeLog-2.6.34.10">http://www.kernel.org/pub/linux/kernel/v2.6/longterm/v2.6.34/ChangeLog-2.6.34.10</a>

100

101

102

103

104

105

106

107

108

109

110

111

112

113

114

115

116

117

118

119

120

121

122

123

124

125

126

127

128

129

130

131

132

133

134

135

136

137

138

139

140

141

142

143

144

145

146

147

148

149

150

151

152

153

154

155

156

157

158

159

160

161

162

163

164

165

166

167

168

169

170

171

172

173

174

175

176

177

178

179

180

181

182

183

184

185

186

187

188

189

190

191

192

193

194

195

196

197

198

199

200

201

202

203

204

205

206

207

208

209

210

211

212

213

214

215

216

217

218

219

220

221

222

223

224

225

226

227

228

229

230

231

232

233

234

235

236

237

238

239

240

241

242

243

244

245

246

247

248

249

250

251

252

253

254

255

256

257

258

259

260

261

262

263

264

265

266

267

268

269

270

271

272

273

274

275

276

277

278

279

280

281

282

283

284

285

286

287

288

289

290

291

292

293

294

295

296

297

298

299

300

301

302

303

304

305

306

307

308

309

310

311

312

313

314

315

316

317

318

319

320

321

322

323

324

325

326

327

328

329

330

331

332

333

334

335

336

337

338

339

340

341

342

343

344

345

346

347

348

349

350

351

352

353

354

355

356

357

358

359

360

361

362

363

364

365

366

367

368

369

370

371

372

373

374

375

376

377

378

379

380

381

382

383

384

385

386

387

388

389

390

391

392

393

394

395

396

397

398

399

400

401

402

403

404

405

406

407

408

409

410

411

412

413

414

415

416

417

418

419

420

421

422

423

424

425

426

427

428

429

430

431

432

433

434

435

436

commit 0eafe6686c56b91d436265c9098e72a1f8ab4f19

Author: Paul Gortmaker <paul.gortmaker@windriver.com>

Date: Sun Jun 26 12:47:42 2011 -0400

Linux 2.6.34.10

commit 83264a0f19be3fe69f5c9048210bb39402fb57db

Author: Al Viro <viro@ftp.linux.org.uk>

Date: Tue Sep 28 18:50:27 2010 +0100

MIPS: secure_computing, syscall audit: syscall number should in r2, not r0.

commit e5b377a8fb7b05f27647698ac739a0504cb2bf80 upstream.

As it is, audit_syscall_entry() and secure_computing() get the

bogus value (0, in fact)

Signed-off-by: Al Viro <viro@zeniv.linux.org.uk>

Cc: linux-kernel@vger.kernel.org

Cc: linux-arch@vger.kernel.org

Cc: linux-mips@linux-mips.org

Patchwork: https://patchwork.linux-mips.org/patch/1697/

Signed-off-by: Ralf Baechle <ralf@linux-mips.org>

Signed-off-by: Paul Gortmaker <paul.gortmaker@windriver.com>

commit 48adbc4b330cefb3b77111e47c17e833404893ef

Author: Linus Torvalds <torvalds@linux-foundation.org>

Date: Thu Oct 28 15:40:55 2010 +0000

net: fix rds_iovec page count overflow

commit 1b1f693d7ad6d193862dcb1118540a030c5e761f upstream.

As reported by Thomas Pollet, the rdma page counting can overflow. We

get the rdma sizes in 64-bit unsigned entities, but then limit it to

UINT_MAX bytes and shift them down to pages (so with a possible "+1" for

an unaligned address).

So each individual page count fits comfortably in an 'unsigned int' (not

even close to overflowing into signed), but as they are added up, they

might end up resulting in a signed return value. Which would be wrong.

Catch the case of tot_pages turning negative, and return the appropriate

error code.

[PG: In 34, var names are slightly different, 1b1f6's tot_pages is

34's nr_pages, and 1b1f6's nr_pages is 34's nr; so map accordingly.]

Reported-by: Thomas Pollet <thomas.pollet@gmail.com>

Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>

Signed-off-by: Andy Grover <andy.grover@oracle.com>

Signed-off-by: David S. Miller <davem@davemloft.net>

Signed-off-by: Paul Gortmaker <paul.gortmaker@windriver.com>

commit e0843d17d6d9997f23534f1ffe9dafb0d5912636

Author: Vasiliy Kulikov <segoon@openwall.com>

Date: Thu Mar 17 01:40:10 2011 +0000

econet: 4 byte infoleak to the network

commit 67c5c6cb8129c595f21e88254a3fc6b3b841ae8e upstream.

struct aunhdr has 4 padding bytes between 'pad' and 'handle' fields on

x86_64. These bytes are not initialized in the variable 'ah' before

sending 'ah' to the network. This leads to 4 bytes kernel stack

infoleak.

This bug was introduced before the git epoch.

Signed-off-by: Vasiliy Kulikov <segoon@openwall.com>

Acked-by: Phil Blundell <philb@gnu.org>

Signed-off-by: David S. Miller <davem@davemloft.net>

Signed-off-by: Paul Gortmaker <paul.gortmaker@windriver.com>

commit 3e3b57978a0e1140d91f09d3a4197b6411b18f12

Author: Vasiliy Kulikov <segoon@openwall.com>

Date: Tue Mar 15 13:37:13 2011 +0100

ipv6: netfilter: ip6_tables: fix infoleak to userspace

commit 6a8ab060779779de8aea92ce3337ca348f973f54 upstream.

Structures ip6t_replace, compat_ip6t_replace, and xt_get_revision are

copied from userspace. Fields of these structs that are

zero-terminated strings are not checked. When they are used as argument

to a format string containing "%s" in request_module(), some sensitive

information is leaked to userspace via argument of spawned modprobe

process.

The first bug was introduced before the git epoch; the second was

introduced in 3bc3fe5e (v2.6.25-rc1); the third is introduced by

6b7d31fc (v2.6.15-rc1). To trigger the bug one should have

CAP_NET_ADMIN.

Signed-off-by: Vasiliy Kulikov <segoon@openwall.com>

Signed-off-by: Patrick McHardy <kaber@trash.net>

Signed-off-by: Paul Gortmaker <paul.gortmaker@windriver.com>

commit 1d9064bb2d8f0ea26a67b2ce74c6d1d461dcfe7d

Author: Vasiliy Kulikov <segoon@openwall.com>

Date: Tue Mar 15 13:36:05 2011 +0100

netfilter: ip_tables: fix infoleak to userspace

commit 78b79876761b86653df89c48a7010b5cbd41a84a upstream.

Structures ipt_replace, compat_ipt_replace, and xt_get_revision are

copied from userspace. Fields of these structs that are

zero-terminated strings are not checked. When they are used as argument

to a format string containing "%s" in request_module(), some sensitive

information is leaked to userspace via argument of spawned modprobe

process.

The first and the third bugs were introduced before the git epoch; the

second was introduced in 2722971c (v2.6.17-rc1). To trigger the bug

one should have CAP_NET_ADMIN.

Signed-off-by: Vasiliy Kulikov <segoon@openwall.com>

Signed-off-by: Patrick McHardy <kaber@trash.net>

Signed-off-by: Paul Gortmaker <paul.gortmaker@windriver.com>

commit f1f486501fa9b401c762b2355a238cf9e7f18385

Author: Vasiliy Kulikov <segoon@openwall.com>

Date: Tue Mar 15 13:35:21 2011 +0100

netfilter: arp_tables: fix infoleak to userspace

commit 42eab94fff18cb1091d3501cd284d6bd6cc9c143 upstream.

Structures ipt_replace, compat_ipt_replace, and xt_get_revision are

copied from userspace. Fields of these structs that are

zero-terminated strings are not checked. When they are used as argument

to a format string containing "%s" in request_module(), some sensitive

information is leaked to userspace via argument of spawned modprobe

process.

The first bug was introduced before the git epoch; the second is

introduced by 6b7d31fc (v2.6.15-rc1); the third is introduced by

6b7d31fc (v2.6.15-rc1). To trigger the bug one should have

CAP_NET_ADMIN.

Signed-off-by: Vasiliy Kulikov <segoon@openwall.com>

Signed-off-by: Patrick McHardy <kaber@trash.net>

Signed-off-by: Paul Gortmaker <paul.gortmaker@windriver.com>

commit 41c6364db6028e2776250be12961b30f4a2ffbf9

Author: Vasiliy Kulikov <segoon@openwall.com>

Date: Mon Feb 14 16:49:23 2011 +0100

bridge: netfilter: fix information leak

commit d846f71195d57b0bbb143382647c2c6638b04c5a upstream.

Struct tmp is copied from userspace. It is not checked whether the "name"

field is NULL terminated. This may lead to buffer overflow and passing

contents of kernel stack as a module name to try_then_request_module() and,

consequently, to modprobe commandline. It would be seen by all userspace

processes.

Signed-off-by: Vasiliy Kulikov <segoon@openwall.com>

Signed-off-by: Patrick McHardy <kaber@trash.net>

Signed-off-by: Paul Gortmaker <paul.gortmaker@windriver.com>

commit 26b6a59e8b70435996c86f705dfb7f66124f5b1e

Author: Vasiliy Kulikov <segoon@openwall.com>

Date: Mon Feb 14 13:54:31 2011 +0300

Bluetooth: bnep: fix buffer overflow

commit 43629f8f5ea32a998d06d1bb41eefa0e821ff573 upstream.

Struct ca is copied from userspace. It is not checked whether the "device"

field is NULL terminated. This potentially leads to BUG() inside of

alloc_netdev_mqs() and/or information leak by creating a device with a name

made of contents of kernel stack.

Signed-off-by: Vasiliy Kulikov <segoon@openwall.com>

Signed-off-by: Gustavo F. Padovan <padovan@profusion.mobi>

Signed-off-by: Paul Gortmaker <paul.gortmaker@windriver.com>

commit f8107dd119c9fd62aa0a3d3eb55d67bdd84b8036

Author: Vasiliy Kulikov <segoon@openwall.com>

Date: Mon Feb 14 13:54:26 2011 +0300

Bluetooth: sco: fix information leak to userspace

commit c4c896e1471aec3b004a693c689f60be3b17ac86 upstream.

struct sco_conninfo has one padding byte in the end. Local variable

cinfo of type sco_conninfo is copied to userspace with this uninizialized

one byte, leading to old stack contents leak.

Signed-off-by: Vasiliy Kulikov <segoon@openwall.com>

Signed-off-by: Gustavo F. Padovan <padovan@profusion.mobi>

Signed-off-by: Paul Gortmaker <paul.gortmaker@windriver.com>

commit 973800f01aa1ab2bf5b8a412af07fc2cc568c783

Author: Alex Elder <aelder@sgi.com>

Date: Tue Mar 1 17:50:00 2011 +0000

xfs: zero proper structure size for geometry calls

commit af24ee9ea8d532e16883251a6684dfa1be8eec29 upstream.

Commit 493f3358cb289ccf716c5a14fa5bb52ab75943e5 added this call to

xfs_fs_geometry() in order to avoid passing kernel stack data back

to user space:

+ memset(geo, 0, sizeof(*geo));

Unfortunately, one of the callers of that function passes the

address of a smaller data type, cast to fit the type that

xfs_fs_geometry() requires. As a result, this can happen:

Kernel panic - not syncing: stack-protector: Kernel stack is corrupted

in: f87aca93

Pid: 262, comm: xfs_fsr Not tainted 2.6.38-rc6-493f3358cb2+ #1

Call Trace:

[<c12991ac>] ? panic+0x50/0x150

[<c102ed71>] ? __stack_chk_fail+0x10/0x18

[<f87aca93>] ? xfs_ioc_fsgeometry_v1+0x56/0x5d [xfs]

Fix this by fixing that one caller to pass the right type and then

copy out the subset it is interested in.

Note: This patch is an alternative to one originally proposed by

Eric Sandeen.

Reported-by: Jeffrey Hundstad <jeffrey.hundstad@mnsu.edu>

Signed-off-by: Alex Elder <aelder@sgi.com>

Reviewed-by: Eric Sandeen <sandeen@redhat.com>

Tested-by: Jeffrey Hundstad <jeffrey.hundstad@mnsu.edu>

Signed-off-by: Paul Gortmaker <paul.gortmaker@windriver.com>

commit 5658d0e0d4830af95fcde40bc7c6db2dec8ebddf

Author: Dan Rosenberg <drosenberg@vsecurity.com>

Date: Mon Feb 14 13:45:28 2011 +0000

xfs: prevent leaking uninitialized stack memory in FSGEOMETRY_V1

commit 3a3675b7f23f83ca8c67c9c2b6edf707fd28d1ba upstream.

The FSGEOMETRY_V1 ioctl (and its compat equivalent) calls out to

xfs_fs_geometry() with a version number of 3. This code path does not

fill in the logsunit member of the passed xfs_fsop_geom_t, leading to

the leaking of four bytes of uninitialized stack data to potentially

unprivileged callers.

v2 switches to memset() to avoid future issues if structure members

change, on suggestion of Dave Chinner.

Signed-off-by: Dan Rosenberg <drosenberg@vsecurity.com>

Reviewed-by: Eugene Teo <eugeneteo@kernel.org>

Signed-off-by: Alex Elder <aelder@sgi.com>

Signed-off-by: Paul Gortmaker <paul.gortmaker@windriver.com>

commit 11c66be05f49f70a635a6eb63e6cffea520b22c5

Author: Dan Rosenberg <drosenberg@vsecurity.com>

Date: Sun Dec 26 06:54:53 2010 +0000

CAN: Use inode instead of kernel address for /proc file

commit 9f260e0efa4766e56d0ac14f1aeea6ee5eb8fe83 upstream.

Since the socket address is just being used as a unique identifier, its

inode number is an alternative that does not leak potentially sensitive

information.

CC-ing stable because MITRE has assigned CVE-2010-4565 to the issue.

Signed-off-by: Dan Rosenberg <drosenberg@vsecurity.com>

Acked-by: Oliver Hartkopp <socketcan@hartkopp.net>

Signed-off-by: David S. Miller <davem@davemloft.net>

Signed-off-by: Paul Gortmaker <paul.gortmaker@windriver.com>

commit 5cf8a08026f539f396a3170d1991d651ee0fb30c

Author: Dan Rosenberg <drosenberg@vsecurity.com>

Date: Wed Dec 22 13:58:27 2010 +0000

irda: prevent integer underflow in IRLMP_ENUMDEVICES

commit fdac1e0697356ac212259f2147aa60c72e334861 upstream.

If the user-provided len is less than the expected offset, the

IRLMP_ENUMDEVICES getsockopt will do a copy_to_user() with a very large

size value. While this isn't be a security issue on x86 because it will

get caught by the access_ok() check, it may leak large amounts of kernel

heap on other architectures. In any event, this patch fixes it.

Signed-off-by: Dan Rosenberg <drosenberg@vsecurity.com>

Signed-off-by: David S. Miller <davem@davemloft.net>

Signed-off-by: Paul Gortmaker <paul.gortmaker@windriver.com>

commit 32e92da012e081ce4f741974761e92b215ff58b5

Author: Nelson Elhage <nelhage@ksplice.com>

Date: Wed Nov 3 16:35:40 2010 +0000

netlink: Make nlmsg_find_attr take a const nlmsghdr*.

commit 6b8c92ba07287578718335ce409de8e8d7217e40 upstream.

This will let us use it on a nlmsghdr stored inside a netlink_callback.

Signed-off-by: Nelson Elhage <nelhage@ksplice.com>

Signed-off-by: David S. Miller <davem@davemloft.net>

Signed-off-by: Paul Gortmaker <paul.gortmaker@windriver.com>

commit 02e6f1ee075a325dc9079b3dc143d898e924ce64

Author: Nelson Elhage <nelhage@ksplice.com>

Date: Wed Nov 3 16:35:41 2010 +0000

inet_diag: Make sure we actually run the same bytecode we audited.

commit 22e76c849d505d87c5ecf3d3e6742a65f0ff4860 upstream.

We were using nlmsg_find_attr() to look up the bytecode by attribute when

auditing, but then just using the first attribute when actually running

bytecode. So, if we received a message with two attribute elements, where only

the second had type INET_DIAG_REQ_BYTECODE, we would validate and run different

bytecode strings.

Fix this by consistently using nlmsg_find_attr everywhere.

Signed-off-by: Nelson Elhage <nelhage@ksplice.com>

Signed-off-by: Thomas Graf <tgraf@infradead.org>

Signed-off-by: David S. Miller <davem@davemloft.net>

Signed-off-by: Paul Gortmaker <paul.gortmaker@windriver.com>

commit ddfd87424bef1dc8b2930acae2311b286ab9de12

Author: Kulikov Vasiliy <segooon@gmail.com>

Date: Sun Oct 31 07:10:32 2010 +0000

net: tipc: fix information leak to userland

commit 88f8a5e3e7defccd3925cabb1ee4d3994e5cdb52 upstream.

Structure sockaddr_tipc is copied to userland with padding bytes after

"id" field in union field "name" unitialized. It leads to leaking of

contents of kernel stack memory. We have to initialize them to zero.

Signed-off-by: Vasiliy Kulikov <segooon@gmail.com>

Signed-off-by: David S. Miller <davem@davemloft.net>

Signed-off-by: Paul Gortmaker <paul.gortmaker@windriver.com>

commit 262b3d2e9f111516bf5cc1211f9128180e0329ef

Author: Vasiliy Kulikov <segooon@gmail.com>

Date: Wed Nov 10 10:14:33 2010 -0800

net: ax25: fix information leak to userland

commit fe10ae53384e48c51996941b7720ee16995cbcb7 upstream.

Sometimes ax25_getname() doesn't initialize all members of fsa_digipeater

field of fsa struct, also the struct has padding bytes between

sax25_call and sax25_ndigis fields. This structure is then copied to

userland. It leads to leaking of contents of kernel stack memory.

Signed-off-by: Vasiliy Kulikov <segooon@gmail.com>

Signed-off-by: David S. Miller <davem@davemloft.net>

Signed-off-by: Paul Gortmaker <paul.gortmaker@windriver.com>

commit 44a214c1611386aa49ce86c70ebcddcad8a7a3f0

Author: Stuart Hayes <stuart_hayes@yahoo.com>

Date: Wed Mar 2 13:42:05 2011 +0100

dcdbas: force SMI to happen when expected

commit dd65c736d1b5312c80c88a64bf521db4959eded5 upstream.

The dcdbas driver can do an I/O write to cause a SMI to occur. The SMI handler

looks at certain registers and memory locations, so the SMI needs to happen

immediately. On some systems I/O writes are posted, though, causing the SMI to

happen well after the "outb" occurred, which causes random failures. Following

the "outb" with an "inb" forces the write to go through even if it is posted.

Signed-off-by: Stuart Hayes <stuart_hayes@yahoo.com>

Acked-by: Doug Warzecha <douglas_warzecha@dell.com>

Signed-off-by: Jiri Kosina <jkosina@suse.cz>

Signed-off-by: Paul Gortmaker <paul.gortmaker@windriver.com>

commit e4b2f0cae9c5cd1d5a0959ee529e6a6fee620c5c

Author: Josef Bacik <josef@redhat.com>

Date: Thu Nov 18 20:52:55 2010 -0500

fs: call security_d_instantiate in d_obtain_alias V2

commit 24ff6663ccfdaf088dfa7acae489cb11ed4f43c4 upstream

While trying to track down some NFS problems with BTRFS, I kept noticing I was

getting -EACCESS for no apparent reason. Eric Paris and printk() helped me

figure out that it was SELinux that was giving me grief, with the following

denial

type=AVC msg=audit(1290013638.413:95): avc: denied { 0x800000 } for pid=1772

comm="nfsd" name="" dev=sda1 ino=256 scontext=system_u:system_r:kernel_t:s0

tcontext=system_u:object_r:unlabeled_t:s0 tclass=file

Turns out this is because in d_obtain_alias if we can't find an alias we create

one and do all the normal instantiation stuff, but we don't do the

security_d_instantiate.

Usually we are protected from getting a hashed dentry that hasn't yet run

security_d_instantiate() by the parent's i_mutex, but obviously this isn't an

option there, so in order to deal with the case that a second thread comes in

and finds our new dentry before we get to run security_d_instantiate(), we go

ahead and call it if we find a dentry already. Eric assures me that this is ok

as the code checks to see if the dentry has been initialized already so calling

security_d_instantiate() against the same dentry multiple times is ok. With

this patch I'm no longer getting errant -EACCESS values.

Signed-off-by: Josef Bacik <josef@redhat.com>

Signed-off-by: Al Viro <viro@zeniv.linux.org.uk>

Signed-off-by: Paul Gortmaker <paul.gortmaker@windriver.com>

commit 0ec63bc8c16763ab565ab97d39f10eb9a6ab9125

Author: Robin Holt <holt@sgi.com>

Date: Wed Jan 12 17:00:01 2011 -0800

epoll: convert max_user_watches to long

commit 52bd19f7691b2ea6433aef0ef94c08c57efd7e79 upstream.

On a 16TB machine, max_user_watches has an integer overflow. Convert it

to use a long and handle the associated fallout.

Signed-off-by: Robin Holt <holt@sgi.com>

Cc: "Eric W. Biederman" <ebiederm@xmission.com>

Acked-by: Davide Libenzi <davidel@xmailserver.org>

Cc: Pekka Enberg <penberg@cs.helsinki.fi>

Signed-off-by: Andrew Morton <akpm@linux-foundation.org>

Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>

Signed-off-by: Paul Gortmaker <paul.gortmaker@windriver.com>

O resto pode ser visto em: <a href="http://www.kernel.org/pub/linux/kernel/v2.6/longterm/v2.6.34/ChangeLog-2.6.34.10">http://www.kernel.org/pub/linux/kernel/v2.6/longterm/v2.6.34/ChangeLog-2.6.34.10</a>

Sabayon Linux 6

24/06/2011 by OwnServer

Foi lançado recentemente o Sabayon Linux 6, é um projeto totalmente baseado no Gentoo. Um sistema operacional de alto nível, com tota flexibilidade que o Gentoo tem porém com um toque a mais de user-friendly.

O fino dele é a preservação do Gnome 2.32 como plataforma gráfica (ambiente X). KDE 4.6.4 também está como alternativa para os usuários.
O kernel usado é 2.6.39.1, o btrfs está nativo no núcleo do sistema e sua parte de artwork e music boot splash foram mudados.
Existem outras características importantes que podem ser conferidas aqui:

Press Release: Sabayon Linux 6 GNOME and KDE

We’re once again here to announce the immediate availability of Sabayon 6, one of the biggest milestone in our project.
Letting bleeding edge and reliability to coexist is the most outstanding challenge our users, our team, is faced every day.
There you have it, shining at full bright, for your home computer, your laptop and your home servers.
Because we do care about our community, we do listen to our users, we consider them part of the game, we decided to leave GNOME3 out for another, last, release cycle, in order let things to settle down: providing a broken user experience has never been in our plans.
Besides, what do we have under the hood this round? Let’s go ahead and see.

Please don’t forget to donate here, we still need your support.
Thanks to your donations, we were able to buy a new development server, but we need more I/O speed now!

Features

Linux Kernel 2.6.39.1 and blazing fast, yet reliable, boot
Providing extra Server-optimized, OpenVZ-enabled, Vserver-enabled kernels in repositories
Natively supporting btrfs filesystem
Completely reworked artwork and boot music intro, thanks to our little Van Gogh (Ian Whyman)
Improved theming for 16:9 and 16:10 widescreen monitors
Transform Sabayon into an full-featured HTPC Operating System (Media Center) using XBMC
Entropy 1.0_rc10, bringing outstanding speed and reliability. Entropy Store (Sulfur) went through a massive speed rework. Entropy Web Services foundation library has been introduced in order to support User Generated Content contributions in a more powerful way, bringing our Package Manager in the Social Internet age. Added support to delta packages downloads, parallel packages download, differential repository update through simple HTTPS protocol
Several Sabayon Installer improvements, especially with dealing with crypt, LVM and swRAID environments
Added a non-intrusive firewall tool called “ufw” and its frontends for GNOME and KDE
X.Org Server updated to 1.10
Sane Desktop Compositing now enabled by default
Switched to IcedTea6 as bundled Java VM
Switched to jpeg-turbo library, boosting JPEG images rendering speed
Switched to LibreOffice 3.3.3
Switched to Chromium/WebKit as bundled Web Browser
Split nvidia-drivers and ati-drivers into userspace and kernel modules, improving reliability over kernel migrations
Updated to GNOME 2.32.2 and KDE 4.6.4
Updated to GRUB 1.99
Introduced the “kernel-switcher” tool, to easily switch between available Sabayon Linux kernels
Python toolchain updated to version 2.7
Updated to GCC 4.5.2
Dracut and Plymouth ready (expect them in Sabayon 7)
Thousands of updates and bug fixes that flew in, during these last 4 months
We’re still here! (it’s a feature), only thanks to your donations, please keep donating, donate now!

Minimum requirements (aka, we don’t underestimate them, like everybody else does):

An i686-compatible Processor (Intel Pentium II/III, Celeron, AMD Athlon)
512Mb RAM (GNOME) – 768Mb RAM (KDE)
8 GB of free space
A X.Org supported 2D GPU
A DVD reader

Optimal requirements

A Dual Core Processor (Intel Core 2 Duo or better, AMD Athlon 64 X2 or better)
1024Mb RAM
15 GB of free space
A X.Org supported 3D GPU (Intel, AMD, NVIDIA) (esp. for XBMC)

Download sources
ISO images (those little .iso files that you have download and burn) are available on our mirrors:

Sabayon Linux 6 amd64 (x86_64, x64) GNOME:
06b51b1b0210a636c40a0eba1822539c Sabayon_Linux_6_amd64_G.iso
Sabayon Linux 6 x86 (i686, x32) GNOME:
76ce8f9871940573a5841123348def29 Sabayon_Linux_6_x86_G.iso
Sabayon Linux 6 amd64 (x86_64, x64) KDE:
ce2d774270bb8c020aedf76f5f57e5bb Sabayon_Linux_6_amd64_K.iso
Sabayon Linux 6 x86 (i686, x32) KDE:
68ece268e181967b8200382b019e3c0b Sabayon_Linux_6_x86_K.iso
Sabayon Mirrors Page
Sabayon Bittorrent Tracker

Para baixar veja:

Sabayon_Linux_6_x86_K.iso (1,956MB, MD5, torrent), Sabayon_Linux_6_x86_G.iso (1,561MB, MD5, torrent), Sabayon_Linux_6_amd64_K.iso (2,180MB, MD5, torrent), Sabayon_Linux_6_amd64_G.iso (1,777MB, MD5, torrent).

Mageia Linux 1 Lançado!

02/06/2011 by OwnServer

Mageia Linux foi lançado recentemente em sua versão ULTRA estável. Uma das coisas que devemos evidenciar/reverenciar é a forma que os desenvolveores do Mageia Linux Trabalham afim de lançar releases muito consistentes. Se você quer conferir a história do Mageia Linux pode acessar nosso portal de Linux (nosso site, e escolha a categoria do Mageia). Nosso já fizemos (fomos os primeiros no Brasil) how tos completos sobre Mageia Linux, esta distribuição, tanto no que tange a origem do Mageia como também no Uso e configurações iniciais do Mageia como desktop (assim como suporte a redes). Usamos o Gnome afim de alcançarmos o máximo de estabilidade na fase beta.

Veja as notas de lançamento:

Major features in Mageia

Package Management tools

Mageia uses the all too familiar urpmi, this the default dependency resolver in Mageia, you can use to install RPM packages on the system. It can also be used to update the system, for the full usage details check the urpmi man page.

The rest of the family are:

urpme: used to uninstall RPM packages installed on the system, with many command line options
urpmf: a tool that can be used to show what package contains a certain file; it can also be used to search for all sorts of RPM tags (requires, suggests, conflicts, obsoletes) in the packages in the official repositories, among other features
urpmq: the urpmi database query tool, think of it as ‘rpm -q’ but with many more extended features, that can be used to check RPM packages in the official repositories
urpmi.update: a tool to update the urpmi database on the user’s installation, it can also be used to disable (ignore) configured media sources on the system
urpmi.addmedia: a tool to add the Mageia media sources (online (http, ftp, rsync) and local alike)
urpmi.removemedia: a tool to remove the media sources configured on the system

Mageia system configuration tools

Mageia will go on using all the familiar drak tools; here’re the highlights:

drakconf: The Mageia control center, which can be used to launch all sorts of system administration tools
drak3d: A tool to to configure 3D desktop effects (e.g. Compiz)
drakguard: A tool that allows to configure parental control. It can block access to web sites and restrict the internet connection to specific timeframe
rpmdrake: A simple interface that makes it easy to install and remove software packages (RPM) in Mageia
drakx-net: The default Mageia network tools
userdrake: A user-friendly and powerful tool for administrating users and groups
system-config-printer: A powerful printer configuration tool, developed by Redhat/Fedora

Migration from Mandriva Linux

If you are using Mandriva Linux 2010.1 or 2010.2, see our migration guide.

Available Desktop Environments

As a desktop-agnostic distribution, Mageia has all the popular desktop environments, along with various window managers. Here’s an overview of them:

KDE4

KDE SC 4.6.3. This release brings many improvements and new features for more details check the release announcement.

GNOME

GNOME 2.32, with the plethora of popular applications that come with it (Totem, Rhythmbox, Epiphany, Evolution, The GNOME Archiver (file-roller), Evince, F-Spot… etc).

XFCE4

The latest stable version, 4.8.1, of XFCE, it brings many improvements, for the full details have a look at the XFCE 4.8 release announcement.

LXDE

Latest stable LXDE packages (PCManFM, LXSession, LXTerminal, Gpicview, LXRandR).

Window Managers

Various other window managers, which in reality they’re just small and very lightweight desktop environments:

Openbox
WindowMaker
IceWM
Fluxbox
Fvwm2

Desktop Applications

A lot of the popular desktop applications, here are the highlights.

Web Browsers and email clients

Firefox: Firefox 4.0.1., this new release brings with it a lot of improvements concerning all aspects of Firefox, for more info have a look at the Firefox 4 release notes
Chromium-Browser: Google Chromium-browser 11.0.696.65., and for users’ convenience the Chromium-browser comes in three different flavours, stable, beta and unstable, each one following a different upstream channel/branch, needless to say that beta and unstable are not for the weak of heart!
Epiphany: The latest stable version, 2.30.6, of the GNOME web browser based on the webkit rendering engine is available in the Mageia repos
KMail: The latest stable version, 4.4.11.1, of the famous KDE4 email client
Thunderbird: The latest stable version of the famous email client from Mozilla, Thunderbird 3.1.10, is available in the online repositories, with all the improvements and fixes in the 3.1.x series, for more info have a look at the release notes. Both Enigmail and Lightning extensions are available too
Evolution: The latest stable version, 2.32.2, of the famous GNOME mailer, calendar, contact manager and communications tool.

Office

LibreOffice: Mageia promised to fully support LibreOffice and it’s kept its promise, the stable LibreOffice 3.3.2.2 is available the Mageia repositories, bringing a full suite of office applications
Calligra: The Calligra Suite project is a continuation of the KOffice project, it has all the familiar components of KOffice, for a detailed list of available applications and what they can do check their web site
KmyMoney: The latest stable version, 4.5.3 personal finance manager for KDE4 is already in the online repositories, its mainly focuses on being accurate, easy to use and fully featured with all the familiar features you’d expect in a finance manager
Skrooge: with the philosophy of giving users options, Skrooge 0.8.1 is available in the Mageia repositories too, a personal finance manager for KDE4, it aims to be highly intuitive, while providing powerful functions
GnuCash: GnuCash 2.4.5 is available in the online repositories, it’s comes with a check-book like register GUI that allows you to enter and track your financial matters

Communications

Instant Messaging

Kopete: The latest stable version of the familiar instant messenger, part of KDE SC 4.6.3, is available with support for a wide variety of instant messaging protocol
Pidgin: The latest stable version, 2.7.11, of the famous GTK+2.0 based instant messaging client is available in the online repositories, it supports a plethora of instant messaging protocols. For more details about the fixes and improvements this version brings have a look at the changelog
Empathy: Empathy is an IM client based on the Telepathy framework, Empathy 2.34.0.
Kadu: An instant messenger compatible with the Gadu-Gadu protocol. The latest stable version, 0.9.1

IRC

Quassel: The latest stable version, 0.7.2, of Quassel, a Qt-based modern distributed IRC client is available in the online repositories
Konversation: A fully featured graphical IRC client with KDE support, the latest stable version, 1.3.1, is available in the Mageia online repositories
XChat-gnome: A graphical IRC client for the GNOME desktop. The latest stable version, 0.26.1, is available in the repositories
KVIrc: A Qt-based IRC client with support for themes, transparency, encryption, many extended IRC features, and scripting. The latest stable version, 4.0.4, is available in the repositories

VOIP

QuteCom: A SIP softphone which allows you to make free PC to PC video and voice calls, and to integrate all your IM contacts in one place, it’s Qt-based. The latest stable version 2.2.
Ekiga: A tool to communicate with video and audio over the internet. It uses both SIP and H323 protocol and is compatible with Microsoft Netmeeting. It used to be called GnomeMeeting. The latest stable version, 3.2.7,.

Virtualisation

VirtualBox: Version 4.0.6, of the general-purpose full virtualizer is available in the Mageia repositories
virt-manager: Mageia ships with the latest version of virt-manager (and libvirtd), the popular management toolset for virtualisation, along with binding for various languges, to ease the management of virtual machines, either based on kvm or xen.
WINE: The latest development version of WINE, 1.3.20, is available in the repositories; you can be assured that you’ll usually find the latest version of this famous application in the Backports repository shortly after upstream pushes a new release!

Graphics

Gimp: version 2.6.11 of the famous GNU Image Manipulation Program.
Inkscape: version 0.48.1 of the famous SVG-based vector-drawing program.
Blender: The high quality animation studio. Version 2.49b.

IDEs

Anjuta: A powerful GNOME IDE for C, C++, Python, Java,…
Eclipse: The well known IDE for Java and other languages
Netbeans: The equally well known alternative for eclipse
KDevelop: The KDE IDE

Base System

Mageia ships with the 2.6.38 kernel series, specifically 2.6.38.7 at release time, for more details on the improvements in this kernel series have a look here; the highlights of this kernel:
- Support for automatic process grouping (for more details see Linus Torvalds’ post on LKML (Linux Kernel Mailing list); and mentions of that patch on LWN.net)
- Significant scalability improvements in the Linux VFS (Virtual File System) layer
- Transparent Huge Page support (without using hugetblfs)
- Automatic spreading of outgoing network traffic across multiple CPUs
- Support for the AMD Fusion APUs
- Support for Intel Sandy Bridge and Panther Point.
- Ipset 6.4 with IPv6 support
Boot system: still uses initscripts, 9.21
ALSA 1.0.24.x:
- libalsa2-1.0.24.1
- alsa-plugins-1.0.24
- alsa-tools-1.0.24.1: The firmware bits have been split in a new separate package, alsa-firmware
- alsa-utils-1.0.24.2

X server

X server 1.10.1, with full Udev support (Udev replaces HAL in this regard)
ATI/AMD free radeon driver: Kernel Mode Setting is now enabled by default, bringing performance and compatibility improvements.
Intel Sandy Bridge (2nd Generation Intel® Core™ i7/i5/i3) support according to Intel specifications.
Nouveau: the Nouveau driver is used by default for supported nVidia graphics cards. It brings Kernel Mode Setting support, 2D acceleration, and RandR 1.2 support (for easy multi-monitor setup)

Proprietary graphics cards drivers

The latest versions of both the nVidia and ATI (fglrx) proprietary drivers are available in the Nonfree online repository.

Input Methods

To select the Input Method of your choice, you can use draklocale (“Manage localization of your system” in the Mageia Control Center → System). Mageia 1 will have two input methods:

IBus

IBus support (the Intelligent Input Bus), version 1.3.9 is already available in the official repositories.

SCIM

SCIM (Smart Common Input Method), version 1.4.9, is also available in the official repositories.

Available installation media

Mageia has two distinctive installation media types:

DVD ISO and Dual-arch CD ISO, which use the drakx traditional installer and
Live CD ISO, this is a live ISO which can be used to preview the distribution and can also be used to install Mageia on your HDD

You will always find the download info on the Mageia download page; direct (ftp and http) and BitTorrent downloads are available. For more information, have a look at the Mageia installation media page.

Software online repositories

The packages in Mageia exist in three different repositories/media, depending on what license each package uses.

Here’s an overview of those repositories:

Core:

The Core repository includes packages with free-open-source software, i.e. packages licensed under a free-open-source license, the set of the Core media are added by default and the “Core Release” and “Core Updates” are enabled by default
Nonfree:

The Nonfree repository includes packages that are free-of-charge, i.e. Mageia can redistribute them, but they contain closed-source software (hence the Nonfree name); For example this repository includes the nVidia and ATI graphics cards proprietary drivers, firmware for various Wi-Fi cards… etc. The set of the Nonfree media is added by default and the “Nonfree Release” and “Nonfree Updates” are enabled by default
Tainted:

The Tainted repository includes packages under various licenses, free and nonfree ones, but the main criteria for packages in this repository is that they may infringe patents and copyright laws in some countries in the world (e.g. multimedia codecs needed to play various audio/video files, packages needed to play commercial video DVD… etc); as such the set of the Tainted media is added by default but not enabled by default, i.e. it’s completely opt-in; so check your local laws before using packages from this repository. This repository is only added for the convenience of the users. This repository is to Mageia what PLF is to Mandriva users or RPM Fusion is to Fedora users.

Quer fazer download do Mageia Linux?

Download (mirror list): mageia-dvd-1-i586.iso (3,826MB, MD5, torrent), mageia-dvd-1-x86_64.iso (3,726MB, MD5, torrent). LiveCds com suporte a linguas européis + inglês EUA: mageia-livecd-1-KDE4-i586.iso (693MB, MD5, torrent), mageia-livecd-1-GNOME-i586.iso (621MB, MD5, torrent).

Kernel 2.6.39 é lançado

20/05/2011 by OwnServer

Linus Torvalds anunciou a disponibilidade do kernel 2.6.39, apesar dele estar em incerto se um outro RC teria sido uma opção melhor. “Entretanto, já que estarei na LinuxCon Japão em duas semanas, a escolha pra mim acabou sendo se eu deveria simplesmente lançar, ou arrastar por mais 3 semanas, ou ter uma janela de merge realmente bagunçada com um espaço no meio”. Novidades proeminentes neste lançamento incluem o IPset, o subsistema de controle de mídia, um par de novos escalonadores de fluxo de rede, a tão esperada remoção do “big kernel lock” e mais.

Anúncio: http://lwn.net/Articles/443684/
Mais sobre o IPset: http://ipset.netfilter.org/
Mais na fonte: http://lwn.net/Articles/443506/#Comments

[via] [via]

Stable kernel 2.6.38.3 estável!

15/04/2011 by OwnServer

http://portugaldigital.co.cc/wp-content/uploads/kernel.png

Foi lançado recentemente o stable do kernel 2.6.38.3.

Além de uma lista de correções você encontrará no link abaixo as principais novidades do mesmo:

http://www.kernel.org/pub/linux/kernel/v2.6/ChangeLog-2.6.38.3

Ubuntu 11.04 Beta 2 Lançado!

14/04/2011 by OwnServer

Olá amantes Ubuntu, Ubunteiros e amantes desta maravilhosa distribuição!

Foi disponibilizado há poucos instantes a nova versão do Ubuntu 11.04 Beta 2. Ainda este mês teremos uma versão Stable do Ubuntu 11.04, e como todos sabem, a cada release há uma ansiedade sem igual por parte dos users.

Para conferir as notas de lançamento e anúncio oficial vejam:

https://lists.ubuntu.com/archives/ubuntu-devel-announce/2011-April/000847.html

Para conferir as notas da versão vejam:

https://blueprints.launchpad.net/ubuntu/natty/+specs

Já podemos entender que MUITO em breve teremos o anúncio da Stable, mas vale a pena usar, tanto para report bugs como para também conhecer o que terá de novo na stable version.
Abraços a todos.

Fedora 14: Fazendo um Desktop perfeito com EasyLife :)

06/02/2011 by OwnServer

Todos sabemos que uma das coisas mais chatas que podemos viver é ter de instalar um sistema operacional e depois de instalado (como se não fosse pouco ter de se virar para achar softwares que trabalhem corretamente com os periféricos [ falo de drivers/módulos ] ) e ainda ter de colocar coisas que gostamos (codecs, plugins de navegadores e coisas do tipo).

Neste instante estou usando o Fedora 14 (x86_64), em outras palavras, um Fedora 64 bits. Posso afirmar que o desempenho do mesmo é muito bom quando se trata de uma arquitetura realmente 64 bits (como é o caso do hardware que estou usando).

A dica aqui resume-se na condição de qualquer versão, desde que você queira coisas como skype, fontes agradáveis e coisas do tipo em um ambiente Gnome, vale a pena conferir.
Há muito tempo um pessoal muito dedicado e afiadíssimo no Fedora Linux trabalha otimizando e automatizando a forma com que usuários do Fedora, de maneira “easy-to-use” possa adicionar plugins e coisas complicadas com meros clicks.

O site do projeto é este aqui:

http://easylifeproject.org/

Se possível faça uma doação, pois “o negócio funciona”.

Antes que você prossiga quero confirmar as coisas mais bacanas e funcionais que o Easylife faz para você:

1 – coloca fontes super agradáveis para leitura e usabilidade do sistema operacional em seu ambiente Gnome,

2 – coloca uma skin (tema) muito suave e agradável de se trabalhar,

3 – ativa recursos como Google Desktop, Skype, Codecs de som (sim, nem pense que ouvir mp3 é tão simples assim),

4 – ativa recursos como Jre 6 (java runtime).

Isto em cima é um resumo muito básico, o qual, cada coisa importante pode ser selecionada a dedo e o “trabalho sujo” é feito pelos scripts do easylife que, para variar estão super estruturados e estáveis.

Veja que, ao clicar em Download fomos automaticamente redirecionados para o SourceForge. Pode baixar tranquilamente o arquivo e executá-lo assim que o download for completo.

Assim que terminar, após começar a execução a tela será semelhante a minha:

Depois da escolha dos itens (recomendo marcar tudo, exceto os 2 jre do final, só deve-se marcar 1 de acordo com a arquitetura do seu sistema operacional. Se for x86_64/64 bits escolha 64, se for i386/32 bits escolha 32bits).
A média de arquivos que vão ser baixados do repositório gira em torno de 500 megas (mais um pouco, é claro).

Espere terminar tudo, no final seu sistema estará bem completo.

Das coisas que ressalto para que você possa confiar no Easylife posso dar prioridade a:

1 – ouvir diversos formatos de música,

2 – ouvir muitos formatos de vídeo,

3 – customização clean e rápida do desktop (mudança de fonts, ícones, barras de janelas),

4 – suporte a nvidia [drivers muito bons],

5 – skype e recursos Google.

Terminando todo o download e instalação você verá como a vida fica bem mais easy em cima do Fedora 14 Linux com Easylife.

Parabéns a equipe do Easylife. (versão testada no Fedora 14 pela equipe AppUnix).

Major features in Mageia

Package Management tools

Mageia system configuration tools

Available Desktop Environments

KDE4

GNOME

XFCE4

LXDE

Window Managers

Desktop Applications

Web Browsers and email clients

Office

Communications

Instant Messaging

IRC

VOIP

Virtualisation

Graphics

IDEs

Base System

X server

Proprietary graphics cards drivers

Input Methods

IBus

SCIM

Available installation media

Software online repositories

Core:

Nonfree:

Tainted: