On 05/20/2011 11:14 AM, Bastian Blank wrote:
> On Fri, May 20, 2011 at 10:59:10AM +0200, Bernd Zeimetz wrote:
>> On 05/20/2011 10:40 AM, Bastian Blank wrote:
(And please let me know what is wrong in using dd on a disk drive. I
assume you never read the bugzilla entry on kernel.org.)
>>> d
On Fri, May 20, 2011 at 10:59:10AM +0200, Bernd Zeimetz wrote:
> On 05/20/2011 10:40 AM, Bastian Blank wrote:
> >> (And please let me know what is wrong in using dd on a disk drive. I
> >> assume you never read the bugzilla entry on kernel.org.)
> > dd does not use the sync syscall.
> You obviusly
On 05/20/2011 10:40 AM, Bastian Blank wrote:
>> (And please let me know what is wrong in using dd on a disk drive. I
>> assume you never read the bugzilla entry on kernel.org.)
>
> dd does not use the sync syscall.
You obviusly still did not read the bugzilla entry about this bug.
It mentions su
On Fri, May 20, 2011 at 10:21:39AM +0200, Bernd Zeimetz wrote:
> On 05/20/2011 10:19 AM, Bernd Zeimetz wrote:
> > On 05/20/2011 09:55 AM, Bastian Blank wrote:
> >> The kernel works as documented. It is the task of userspace to use the
> >> correct interface.
> > So what you say is that a kernel is
On 05/20/2011 10:19 AM, Bernd Zeimetz wrote:
> On 05/20/2011 09:55 AM, Bastian Blank wrote:
>> On Fri, May 20, 2011 at 09:19:34AM +0200, Bernd Zeimetz wrote:
>>> If a userspace prgram is able to trigger a kernel bug the kernel needs to be
>>> fixed, not userspace.
>>
>> The kernel works as document
On 05/20/2011 09:55 AM, Bastian Blank wrote:
> On Fri, May 20, 2011 at 09:19:34AM +0200, Bernd Zeimetz wrote:
>> If a userspace prgram is able to trigger a kernel bug the kernel needs to be
>> fixed, not userspace.
>
> The kernel works as documented. It is the task of userspace to use the
> correc
On Fri, May 20, 2011 at 09:19:34AM +0200, Bernd Zeimetz wrote:
> If a userspace prgram is able to trigger a kernel bug the kernel needs to be
> fixed, not userspace.
The kernel works as documented. It is the task of userspace to use the
correct interface.
Bastian
--
To live is always desirable.
reopen 595927
reassign 595927 linux-2.6
found 595927 2.6.38-4
severity 595927 important
thanks
There is no reason why a kernel bug should only be fixed in userspace. If you
look at the kernel.org bugtracker (where this bug was forwarded to!) you'll see
that it is still happening with recent kernel
8 matches
Mail list logo